UI/UX DESIGN & ILLUSTRATION | INTERNSHIP

SYNCHRONY GPT

Designing clearer interactions and system states for Synchrony’s internal AI experience.

Synchrony GPT 404 page on a laptop Synchrony GPT no-access screen on a phone
TIMELINE

Jan 2026 – Present

ROLE

UI/UX Designer & Illustrator

TOOLS

Figma, FigJam

TEAM

Synchrony GPT team

1
Context OVERVIEW

Synchrony GPT is the company’s internal AI chatbot. Across two internships with the GPT team, and continuing now, I have worked on the moments around the conversation: the system states people hit when something is loading, missing, restricted, or finished.

Problem

System-state screens in the chatbot experience feel less engaging when they lack visual elements, which can reduce user interaction and overall engagement.

How might we

How might we enhance the chatbot experience with appropriate visual elements and illustrations so it feels more interactive and increases user engagement?

PASSWORD PROTECTED

Because this work was done inside Synchrony, the research, design explorations, and final screens are password protected. Please reach out and I am happy to share access.

That password isn’t right — try again.
2
Spring PRELIMINARY RESEARCH

I audited the existing states first. The error screens leaned almost entirely on text: an oversized empty canvas, a headline, and a button, with no visual cue about what had happened or what to do next.

Existing Synchrony 404 error state
Excessive empty space, minimal visual feedback.
Insight 1

Users scan system-state screens quickly. People usually do not read long blocks of text during loading, error, or waiting states.

Insight 2

Visuals make status messages easier to understand. Illustrations and visual cues help users understand what is happening faster.

Insight 3

Engaging system states improve overall experience. Even brief moments like loading or error screens can shape how polished and interactive the product feels.

3
Spring UNDERSTANDING SYNCHRONY GUIDELINES

Before drawing anything I studied the illustration guidelines: simplified rendering, organic lines and shapes, a clean and uncluttered look, subjects that are easy to read at a glance, and an inclusive cast. Just as useful were the don’ts — no unedited stock, no colors outside the approved palette, no linear or cartoon-like illustration, no rigid shapes.

Synchrony illustration guidelines: style rules, don’ts, stock transformation, and palette
The rules an illustration had to satisfy, and recoloring, reshading, and reworking a stock base into the house style.
4
Spring ILLUSTRATION PROCESS

From there I built the set: the GPT robot, the locked-phone access state, the 404 traveler, the maintenance scene, the empty mailbox, and the balloon. Each had to carry its message without making the moment feel technical or like a failure.

Page not found — light mode Page not found — dark mode
Page not found — light and dark mode.
Down for maintenance — light mode Down for maintenance — dark mode
Down for maintenance — light and dark mode.
No access — light mode No access — dark mode
No access — light and dark mode.
Securely signed out — light mode Securely signed out — dark mode
Securely signed out — light and dark mode.
5
Spring result RESPONSIVE DESIGN

The states shipped across mobile and desktop: onboarding, no access, 404, and maintenance, each carrying the same illustration language in both light and dark surfaces.

Onboarding on mobile
No access on mobile
Page not found on desktop
Down for maintenance on desktop
6
Summer NO ACCESS SCREENS

Returning in the summer, I took on the “No Access” experience. Two groups land on this screen — exempt employees who can request access directly, and non-exempt employees and consultants who have to get approval first — and the page had to separate them without burying either path.

Low fidelity

I blocked out the structure first — illustration, headline, the two step groups, and the fallback card — before committing to any visual detail.

Low fidelity wireframe — light mode
Wireframe — light mode.
Low fidelity wireframe — dark mode
Wireframe — dark mode.
No access concept 1
Single stacked list
No access concept 2
Split by employee type
No access concept 3
Steps in one row, eligibility called out separately
Low- and high-fidelity concepts Prototyped and tested the flow Stakeholder and team feedback Final design
Final no access screen — exempt employees tab Final no access screen — non-exempt employees and consultants tab Final no access screen on mobile
The final screen: numbered steps per group, each with its own action, and a fallback for anyone still stuck.
7
Summer HELP & RESOURCES

A cohesive set of custom pastel illustrations for Help & Resources, plus a refined page layout and hierarchy so the six cards — Features, Release Notes, SharePoint Site, Usage Guidelines, Report an Issue, Send Feedback — scan in one pass.

Every illustration was built against Synchrony’s design system so desktop and mobile stayed consistent, and I worked with designers and stakeholders to deliver production-ready UI assets.

Help & Resources — light mode
Help & Resources — light mode.
Help & Resources — dark mode
Help & Resources — dark mode.
Growth | Reflections KEY TAKEAWAYS

The biggest shift was learning to design with a purpose. Every illustration I made had a job beyond looking good — it had to tell someone what was happening on a screen they were only going to glance at. I loved that constraint. Working inside an established design system meant I could not invent my way out of a problem, so the clarity had to come from hierarchy, wording, and placement, and getting that right felt better than any pretty screen I have made.

I also got a lot braver about asking questions. Walking into a company this size, I was nervous to speak up at first. What I found was the opposite of what I expected: people were happy to explain things, and asking early saved me from solving the wrong problem more than once. Presenting to designers and stakeholders went from something I dreaded to something I genuinely looked forward to.

Honestly though, the best part was the people. Working with the SYF GPT team and doing two hackathons together taught me how much better an idea gets once you stop protecting it and put it in front of someone. I loved being in the office: the desk conversations, the connection days, the interns I met on the ETC team who I am still close with. That is the reason I am still here today, and the reason this internship ended up meaning far more to me than the work on the screens.